ci: publish to npm with provenance - #3
Merged
Conversation
Adds --provenance to the release publish step so npm records a signed build-provenance attestation (verified GitHub Actions source), matching the attestations @onkernel/cua packages carry. Works with the existing id-token: write + OIDC trusted publishing. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
--provenanceto therelease.ymlpublish step.0.1.0published fine over OIDC but without a provenance attestation (provenance: falseon npm); this makes future releases carry a signed build-provenance attestation tying the tarball to this repo + workflow — the same attestation@onkernel/cuapackages have.No other change. Works with the existing
id-token: write+ trusted publishing already in the workflow.Effect
npm audit signaturescan verify the source.v*tag release;0.1.0(already out) is unaffected.Note
Low Risk
Single CI flag on npm publish; no application, auth, or runtime behavior changes.
Overview
The release workflow’s Publish to npm step now runs
npm publishwith--provenance, so future tag releases emit a signed build-provenance attestation linking the tarball to this repo and GitHub Actions workflow.This aligns
@onkernel/eve-extensionwith packages like@onkernel/cuathat already publish with provenance. Existingid-token: writeand trusted publishing are unchanged; only the publish flags differ. Effect applies on the nextv*release, not on already-published versions such as0.1.0.Reviewed by Cursor Bugbot for commit 7681d9a. Bugbot is set up for automated code reviews on this repo. Configure here.